When I encounter an ERROR, WARNING, or NOTE in my SAS log that I don't understand, my first recourse is to ask my friend (we'll call him "Google") what it could mean. I copy the entire message (or at least 5 or 6 consecutive words from it) into the search box, surrounded by quotes, and see what literal matches come up.
Not all messages indicate a problem; some are meant to be informational. Yet sometimes I need a little help to understand what that information should mean to me. (Here's an example of one that I wouldn't have guessed on my own.)
On the support.sas.com blog, Renee features the top 10 DATA step messages that prompt customers to call SAS Technical Support.
It's a guest post from Kim Wilson in SAS Technical Support, who is an expert in the area. Kim presented a paper at SAS Global Forum 2011; the paper contains even more useful details.
And now, thanks to the magic of indexed content on the support site and my friend Google (or the search box on support.sas.com), Kim's paper is one of the useful links that will pop up when you search on one of those messages.
3 Comments
Kim's #4 (NOTE: THE MEANING OF AN IDENTIFIER AFTER A QUOTED STRING MAY CHANGE IN A FUTURE SAS RELEASE. INSERTING WHITE SPACE BETWEEN A QUOTED STRING AND THE SUCCEEDING IDENTIFIER IS RECOMMENDED.)
also occurs in PROC SQL due to unbalanced quotes.
I always find that adding a few words from my error messages into google brings up forums posts etc. Most times, someone has already asked the question and gotten an answer.
Mr. Posner, Thank you for visiting the blog and adding to the discourse. Having two Duke-associated participants (you along with Doc M.) certainly adds to the prestige. Congratulations on being "Cooler than Me".
-Chris